Fig.~\ref{fig:gmMMfig} illustrates the subset of the GM
metamodel that we manipulated in our transformation
in~\cite{ECMFApaper}\footnote{In this study, we follow the same
obfuscated naming conventions that we used for the GM
metamodel in~\cite{ECMFApaper} for reasons of confidentiality.}.
\begin{figure*}[tbh]
\centering
% \resizebox{0.8\textwidth}{2.0cm}{%{0.8\textwidth}{!} %2.4cm
  \includegraphics[width=0.65\linewidth]{imgs/new_gmMM.jpg}\\[-2ex]
% }
\caption{Subset of the GM metamodel directly used by our transformation
in~\cite{ECMFApaper}.}
\label{fig:gmMMfig}
%\vspace{-0.6cm}
\end{figure*}
The \emph{PhysicalNode} models a physical node on which software is
deployed.
A \emph{PhysicalNode} may contain multiple \emph{Partition}s (i.e., processing
units or memory partitions) on which software is deployed. Multiple
\emph{Module}s can be deployed on a single \emph{Partition}. A \emph{Module} is
an atomic, deployable, and reusable element in a product line and can contain
multiple \emph{Scheduler}s. A \emph{Scheduler} is the basic unit for software
scheduling. It contains behavior-encapsulating entities, and is responsible for
managing services provided or required by the behavior-encapsulating entities.
Each \emph{Scheduler} may provide and/or require \emph{Service}s, which
model the services provided or required by the \emph{Scheduler}.
